Skip to content

Comments

fix(eager): Use isResolvableObject instead of contains before trying to build hashcode#1286

Merged
jasmith-hs merged 2 commits intomasterfrom
use-is-resolvable-instead
Feb 24, 2026
Merged

fix(eager): Use isResolvableObject instead of contains before trying to build hashcode#1286
jasmith-hs merged 2 commits intomasterfrom
use-is-resolvable-instead

Conversation

@jasmith-hs
Copy link
Contributor

  1. using contains can cause a StackOverflowError
  2. If the depth grows very deep, running hashCode can be quite slow, using isResolvableObject will break out before going into too much depth and we won't use hashCode

In cases where we can't use the hashCode of such objects, we just aren't able to check for changes to them

hashcode

1. using `contains` can cause a StackOverflowError
2. If the depth grows very deep, running hashCode can be quite slow,
   using isResolvableObject will break out before going into too much
   depth and we won't use hashCode

In cases where we can't use the hashCode of such objects, we just aren't
able to check for changes to them
@jasmith-hs jasmith-hs changed the title Use isResolvableObject instead of contains before trying to build hashcode fix(eager): Use isResolvableObject instead of contains before trying to build hashcode Feb 23, 2026
@jasmith-hs jasmith-hs merged commit b85a5a4 into master Feb 24, 2026
7 checks passed
@jasmith-hs jasmith-hs deleted the use-is-resolvable-instead branch February 24, 2026 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants